Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicit doc values setting #4560

Closed
jpountz opened this issue Dec 27, 2013 · 1 comment
Closed

Explicit doc values setting #4560

jpountz opened this issue Dec 27, 2013 · 1 comment
Assignees

Comments

@jpountz
Copy link
Contributor

jpountz commented Dec 27, 2013

Right now doc values are enabled on a field if its fielddata format is doc_values at creation time of the field mapper.

So if you create a field with the doc_values fielddata format, then use the update mapping API to change the format to paged_bytes instead and restart the node, the field mapper won't know that it needs to index doc values and the doc_values format won't be usable anymore.

I'd like to have a doc_values setting on the same level as index and store in the mappings that would remain true even when the field data format becomes paged_bytes so that doc values keep being indexed and the fielddata format can be later set to doc_values again.

@ghost ghost assigned jpountz Dec 27, 2013
@s1monw
Copy link
Contributor

s1monw commented Dec 27, 2013

+1 I think this should be antiviral as well.

jpountz added a commit to jpountz/elasticsearch that referenced this issue Dec 27, 2013
Once doc values are enabled on a field, they can't be disabled.

Close elastic#4560
brusic pushed a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014
Once doc values are enabled on a field, they can't be disabled.

Close elastic#4560
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants